Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb68731bb88c96d7eef0bdae87b4a8c274430f6398c5093f6f43fa93e8e30109

Tx prefix hash: 7184472cc04e842b60302db9faf2299e4c7a5de7170510fe96df58633c57c24e
Tx public key: 76ac4578f5ccf0357e8d78f8350001fd8a102dc2080ec4802ee2cbfe5fff0e9e
Timestamp: 1730947019 Timestamp [UCT]: 2024-11-07 02:36:59 Age [y:d:h:m:s]: 00:017:03:19:08
Block: 1148228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12261 RingCT/type: yes/0
Extra: 0176ac4578f5ccf0357e8d78f8350001fd8a102dc2080ec4802ee2cbfe5fff0e9e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2490ed665bd2b257c379282c95c4760f9a63d1f3a36b15d174a8bc384ae0c562 0.600000000000 1633023 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": 1148238, "vin": [ { "gen": { "height": 1148228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2490ed665bd2b257c379282c95c4760f9a63d1f3a36b15d174a8bc384ae0c562" } } ], "extra": [ 1, 118, 172, 69, 120, 245, 204, 240, 53, 126, 141, 120, 248, 53, 0, 1, 253, 138, 16, 45, 194, 8, 14, 196, 128, 46, 226, 203, 254, 95, 255, 14, 158, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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