Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3443f79a2dd0b13511296cdaef5307e54af96f0c931fd3e81fb3606e739fbf20

Tx prefix hash: c0c5db55d2ec559995a6373676487f89b573b7f7111c35f9d96053078b5e0c16
Tx public key: f60a7f4c8714548f21ea42503d997cd3f6653679446ef01cd8144cb41f2481e4
Timestamp: 1723495423 Timestamp [UCT]: 2024-08-12 20:43:43 Age [y:d:h:m:s]: 00:237:18:27:57
Block: 1086527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169823 RingCT/type: yes/0
Extra: 01f60a7f4c8714548f21ea42503d997cd3f6653679446ef01cd8144cb41f2481e402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ef2d58ffad0b0d7a067b261fbe96658b2dbe4d284b7c2fd18192a5f51021d28 0.600000000000 1561124 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1086537, "vin": [ { "gen": { "height": 1086527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ef2d58ffad0b0d7a067b261fbe96658b2dbe4d284b7c2fd18192a5f51021d28" } } ], "extra": [ 1, 246, 10, 127, 76, 135, 20, 84, 143, 33, 234, 66, 80, 61, 153, 124, 211, 246, 101, 54, 121, 68, 110, 240, 28, 216, 20, 76, 180, 31, 36, 129, 228, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8