Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc3b422acb4128391e56fdf5b0cf69e07d12afd4391fc2273354c452d2975910

Tx prefix hash: e4412c2f142e9298cb39e6c1d0bf6b5da92b67460f36705c3ab93cadd6dc13ee
Tx public key: f814bbe61fa617ed40f7e383d669f54593c7dce7fdc730d7264e884e5466e31c
Timestamp: 1731100860 Timestamp [UCT]: 2024-11-08 21:21:00 Age [y:d:h:m:s]: 00:015:13:17:24
Block: 1149508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11119 RingCT/type: yes/0
Extra: 01f814bbe61fa617ed40f7e383d669f54593c7dce7fdc730d7264e884e5466e31c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bee87371621558ad2dd0191c12385ff0a1d15e5346a7a89297c18b4a8e311298 0.600000000000 1634603 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": 1149518, "vin": [ { "gen": { "height": 1149508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bee87371621558ad2dd0191c12385ff0a1d15e5346a7a89297c18b4a8e311298" } } ], "extra": [ 1, 248, 20, 187, 230, 31, 166, 23, 237, 64, 247, 227, 131, 214, 105, 245, 69, 147, 199, 220, 231, 253, 199, 48, 215, 38, 78, 136, 78, 84, 102, 227, 28, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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