Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a417c889c3cdd702b9a5d9a1f9621bf9005e64627cd459533b52a22d1cf28c1

Tx prefix hash: 333a23d4b9850668b389f227daa066be1fce036e604429c8dd5f44616a23df2d
Tx public key: 7032960e960d232bc3a240d7fd65eb646e47e5cd8594d8d46a8a7ef1a5ac8c23
Timestamp: 1740265755 Timestamp [UCT]: 2025-02-22 23:09:15 Age [y:d:h:m:s]: 00:319:20:41:54
Block: 1225095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226461 RingCT/type: yes/0
Extra: 017032960e960d232bc3a240d7fd65eb646e47e5cd8594d8d46a8a7ef1a5ac8c230211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a40fdd3bf531d1752e6ba64683ae1cd8bac47d9ed03b29481d3e41683768fce7 0.600000000000 1711960 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": 1225105, "vin": [ { "gen": { "height": 1225095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a40fdd3bf531d1752e6ba64683ae1cd8bac47d9ed03b29481d3e41683768fce7" } } ], "extra": [ 1, 112, 50, 150, 14, 150, 13, 35, 43, 195, 162, 64, 215, 253, 101, 235, 100, 110, 71, 229, 205, 133, 148, 216, 212, 106, 138, 126, 241, 165, 172, 140, 35, 2, 17, 0, 0, 0, 9, 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