Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa44d66f31f1e379a0a6050804125a51c69218c0ebc59a62f928a13f0ee52a41

Tx prefix hash: 247db97f119d70ca2c53e76ecb299610a0ca3eda2eedbc10e17aca8d78ef3d13
Tx public key: 2d6a4b272a200d7566b2fe7adce4c74939163eed95434d70ce6c3c7a1104b295
Timestamp: 1726073165 Timestamp [UCT]: 2024-09-11 16:46:05 Age [y:d:h:m:s]: 00:117:18:16:20
Block: 1107903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84214 RingCT/type: yes/0
Extra: 012d6a4b272a200d7566b2fe7adce4c74939163eed95434d70ce6c3c7a1104b29502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6ceb4ab86e31e33ea161a030d32e72d3c0c59bf940c87bb109921e84f87c3f6 0.600000000000 1585610 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": 1107913, "vin": [ { "gen": { "height": 1107903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6ceb4ab86e31e33ea161a030d32e72d3c0c59bf940c87bb109921e84f87c3f6" } } ], "extra": [ 1, 45, 106, 75, 39, 42, 32, 13, 117, 102, 178, 254, 122, 220, 228, 199, 73, 57, 22, 62, 237, 149, 67, 77, 112, 206, 108, 60, 122, 17, 4, 178, 149, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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