Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cbe213b2d85658dddba8d2af40e060007fd2d1c7e42d25a7b90531230c7210c

Tx prefix hash: b7f264ebeb5e6e57286df289045ea0692cefc780831678b96e44e3642c7883fa
Tx public key: 857ad34b10a574d78aaa145833e5373979baf5190c57e94a994d37bc4aaef9b6
Timestamp: 1728332149 Timestamp [UCT]: 2024-10-07 20:15:49 Age [y:d:h:m:s]: 00:204:07:06:28
Block: 1126635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145823 RingCT/type: yes/0
Extra: 01857ad34b10a574d78aaa145833e5373979baf5190c57e94a994d37bc4aaef9b602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eaaaf411f4ad2dd892da63c47373f2a5761b47e2bc0f9077b927d22fdf1d8f7d 0.600000000000 1609430 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": 1126645, "vin": [ { "gen": { "height": 1126635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eaaaf411f4ad2dd892da63c47373f2a5761b47e2bc0f9077b927d22fdf1d8f7d" } } ], "extra": [ 1, 133, 122, 211, 75, 16, 165, 116, 215, 138, 170, 20, 88, 51, 229, 55, 57, 121, 186, 245, 25, 12, 87, 233, 74, 153, 77, 55, 188, 74, 174, 249, 182, 2, 17, 0, 0, 0, 2, 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