Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 673d91c2db7578bf98d84c16be11182d49aba4d7e21080ebb92945f021c1d90c

Tx prefix hash: b1af9147fd2228f56cbe38cceb1b88a37581249c85cc3c8b64b6697736448ae7
Tx public key: 6c63b496d68b7b515a1f99983f1fb304d00074b7f0330df77876a2634720c2d0
Timestamp: 1705391950 Timestamp [UCT]: 2024-01-16 07:59:10 Age [y:d:h:m:s]: 01:297:11:28:57
Block: 936423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471433 RingCT/type: yes/0
Extra: 016c63b496d68b7b515a1f99983f1fb304d00074b7f0330df77876a2634720c2d002110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29ad46888f3ac08f6b3b0b4973aacd6c153c60d39a7502eec7d8cfe2686aed3c 0.600000000000 1394449 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": 936433, "vin": [ { "gen": { "height": 936423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29ad46888f3ac08f6b3b0b4973aacd6c153c60d39a7502eec7d8cfe2686aed3c" } } ], "extra": [ 1, 108, 99, 180, 150, 214, 139, 123, 81, 90, 31, 153, 152, 63, 31, 179, 4, 208, 0, 116, 183, 240, 51, 13, 247, 120, 118, 162, 99, 71, 32, 194, 208, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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