Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ca696de6b92bd2c4d4f3b48bfdae8d214ba5ee5c2f66d75b17f53dd71ca6f5

Tx prefix hash: 07b470cb0f0575fb2ad90595ca7a8aa34f9bd532416d398b3ad97fc025beaee0
Tx public key: 47df7bab972025221420102ae53a677c6f3f56a3cea46846b04d6a02328326b3
Timestamp: 1731446688 Timestamp [UCT]: 2024-11-12 21:24:48 Age [y:d:h:m:s]: 00:192:18:17:46
Block: 1152354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137642 RingCT/type: yes/0
Extra: 0147df7bab972025221420102ae53a677c6f3f56a3cea46846b04d6a02328326b3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b037f20ae56015afc462ef91464cdc0c61511d3ca6a79b3eaa1bac38361bfead 0.600000000000 1637951 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": 1152364, "vin": [ { "gen": { "height": 1152354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b037f20ae56015afc462ef91464cdc0c61511d3ca6a79b3eaa1bac38361bfead" } } ], "extra": [ 1, 71, 223, 123, 171, 151, 32, 37, 34, 20, 32, 16, 42, 229, 58, 103, 124, 111, 63, 86, 163, 206, 164, 104, 70, 176, 77, 106, 2, 50, 131, 38, 179, 2, 17, 0, 0, 0, 3, 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