Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 993863b2243ced9387e7fb6a82e4619514edc5d3a9485033c84cd8910d74e6a0

Tx prefix hash: f13f177ba04d3a2ec3788d1d7b80f465937ccc45c321b9110f0ac332e21d0ac7
Tx public key: 0f064a573eccc34d458186b7db44ae5a9c0d3390e07918de9e6b99c6523738b2
Timestamp: 1710011605 Timestamp [UCT]: 2024-03-09 19:13:25 Age [y:d:h:m:s]: 01:022:04:04:58
Block: 974757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276822 RingCT/type: yes/0
Extra: 010f064a573eccc34d458186b7db44ae5a9c0d3390e07918de9e6b99c6523738b20211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d50e26b15f13f2431e88a0779c68575756ef072d3e0069ef142a4cca5c68b0ca 0.600000000000 1434716 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": 974767, "vin": [ { "gen": { "height": 974757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d50e26b15f13f2431e88a0779c68575756ef072d3e0069ef142a4cca5c68b0ca" } } ], "extra": [ 1, 15, 6, 74, 87, 62, 204, 195, 77, 69, 129, 134, 183, 219, 68, 174, 90, 156, 13, 51, 144, 224, 121, 24, 222, 158, 107, 153, 198, 82, 55, 56, 178, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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