Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e326f4cdcc56eed574b93e2ab409c24a0660859ff6298f6b1b5c07de9b268d28

Tx prefix hash: 8c1a254ba8e6e123e0894fafa1e026a35ca8cc0863e02abd2447912d49e03387
Tx public key: 709369b9d1a9dee73ad4cf99030f7247a9c19ac4f8762dee130530c6e29bd446
Timestamp: 1730730894 Timestamp [UCT]: 2024-11-04 14:34:54 Age [y:d:h:m:s]: 00:065:12:53:45
Block: 1146426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46899 RingCT/type: yes/0
Extra: 01709369b9d1a9dee73ad4cf99030f7247a9c19ac4f8762dee130530c6e29bd4460211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad886d70c343d70ca2af8523dcf88207a59505d2e3303d7a9b5dcf8182e3f61e 0.600000000000 1631069 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": 1146436, "vin": [ { "gen": { "height": 1146426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad886d70c343d70ca2af8523dcf88207a59505d2e3303d7a9b5dcf8182e3f61e" } } ], "extra": [ 1, 112, 147, 105, 185, 209, 169, 222, 231, 58, 212, 207, 153, 3, 15, 114, 71, 169, 193, 154, 196, 248, 118, 45, 238, 19, 5, 48, 198, 226, 155, 212, 70, 2, 17, 0, 0, 0, 2, 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