Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0cdbe08af830cecc2bc7142beff678c76a495f125ff765652525b45a0a0b412

Tx prefix hash: 93327f9d99f22766132a021343fb669d4345b932f002ca37d151ee9187b85d8b
Tx public key: c9f2e16dc6d3913737d30b67bbf200dd313b58094b590fbd827cc9e3a8769860
Timestamp: 1685475730 Timestamp [UCT]: 2023-05-30 19:42:10 Age [y:d:h:m:s]: 01:221:12:26:53
Block: 771588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419745 RingCT/type: yes/0
Extra: 01c9f2e16dc6d3913737d30b67bbf200dd313b58094b590fbd827cc9e3a8769860021100000006e6d27f9c000000000000000000

1 output(s) for total of 1.703761601000 dcy

stealth address amount amount idx
00: 135a7bfa3b2a42ffc180ad9b6aa67df64e1f795d25c95dcf49074eb10fc75c1d 1.703761601000 1220961 of 0

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": 771598, "vin": [ { "gen": { "height": 771588 } } ], "vout": [ { "amount": 1703761601, "target": { "key": "135a7bfa3b2a42ffc180ad9b6aa67df64e1f795d25c95dcf49074eb10fc75c1d" } } ], "extra": [ 1, 201, 242, 225, 109, 198, 211, 145, 55, 55, 211, 11, 103, 187, 242, 0, 221, 49, 59, 88, 9, 75, 89, 15, 189, 130, 124, 201, 227, 168, 118, 152, 96, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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