Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ad155270c9b7ec3f35ddcc51a39c4f7587d4ab57fa9b4d237ee55554cbbe066

Tx prefix hash: 2c73814a963203eef99ef21f546029618b55fb2f153caf6b4cb02aba3a190f1f
Tx public key: 9a61bcfe8542b56c6a5fc21271534b2d1f0be260c9465a52cd819ee4e9504ae6
Timestamp: 1720823490 Timestamp [UCT]: 2024-07-12 22:31:30 Age [y:d:h:m:s]: 00:255:22:18:28
Block: 1064398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182823 RingCT/type: yes/0
Extra: 019a61bcfe8542b56c6a5fc21271534b2d1f0be260c9465a52cd819ee4e9504ae602110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 571ce860d823a96a03af8e8371967b24087e620f93ccf50f96e7fee0593698ac 0.600000000000 1534923 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": 1064408, "vin": [ { "gen": { "height": 1064398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "571ce860d823a96a03af8e8371967b24087e620f93ccf50f96e7fee0593698ac" } } ], "extra": [ 1, 154, 97, 188, 254, 133, 66, 181, 108, 106, 95, 194, 18, 113, 83, 75, 45, 31, 11, 226, 96, 201, 70, 90, 82, 205, 129, 158, 228, 233, 80, 74, 230, 2, 17, 0, 0, 0, 16, 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