Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b45b3df9795e2c2511251c114ad9819979d84e6e54817f013588719bcc353f7a

Tx prefix hash: 8b246dc7715004b3381e0d0b0c35866076605e997f896abbf7fe6c3099b6b6f2
Tx public key: ea894cc10ccd490c3732ffb11d651bb61538d49b528c8cc0c4f88c0fb8a36533
Timestamp: 1711384455 Timestamp [UCT]: 2024-03-25 16:34:15 Age [y:d:h:m:s]: 01:002:09:02:35
Block: 986154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262638 RingCT/type: yes/0
Extra: 01ea894cc10ccd490c3732ffb11d651bb61538d49b528c8cc0c4f88c0fb8a365330211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c35fce6639525789c062f5f2589ab922d5a275c8b4b73164c72e6b3507eeeded 0.600000000000 1446381 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": 986164, "vin": [ { "gen": { "height": 986154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c35fce6639525789c062f5f2589ab922d5a275c8b4b73164c72e6b3507eeeded" } } ], "extra": [ 1, 234, 137, 76, 193, 12, 205, 73, 12, 55, 50, 255, 177, 29, 101, 27, 182, 21, 56, 212, 155, 82, 140, 140, 192, 196, 248, 140, 15, 184, 163, 101, 51, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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