Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd753caf0ce14a403053627af5a8f31f2b13cac2b1fd2e4e9a409e06f68d629c

Tx prefix hash: af2bf5795acfe8efc0e920e6e511bb89c3f99cdd4366cc1da9c6fa1e4cc582b5
Tx public key: 1658d3d60a380339da925da6ede9eddef3a511bbed5e2d1ab11c9d9c4d2bf554
Timestamp: 1693360239 Timestamp [UCT]: 2023-08-30 01:50:39 Age [y:d:h:m:s]: 01:219:14:44:46
Block: 836880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418084 RingCT/type: yes/0
Extra: 011658d3d60a380339da925da6ede9eddef3a511bbed5e2d1ab11c9d9c4d2bf55402110000000233af99f4000000000000000000

1 output(s) for total of 1.035307191000 dcy

stealth address amount amount idx
00: d0b6a745917aa9196edbcfff9030aaa1b1f628b11b9647539e991f19a1d2178a 1.035307191000 1289486 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": 836890, "vin": [ { "gen": { "height": 836880 } } ], "vout": [ { "amount": 1035307191, "target": { "key": "d0b6a745917aa9196edbcfff9030aaa1b1f628b11b9647539e991f19a1d2178a" } } ], "extra": [ 1, 22, 88, 211, 214, 10, 56, 3, 57, 218, 146, 93, 166, 237, 233, 237, 222, 243, 165, 17, 187, 237, 94, 45, 26, 177, 28, 157, 156, 77, 43, 245, 84, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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