Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0182e1ba9b431433592e21562d25c68c2186b98e8cca1ac9cd154b6844eac1c

Tx prefix hash: 45098b8290d237091dfe21c7e1f5de317df054e6ceabe42e01d807ba55751d01
Tx public key: 636ef708c42a75c36cd8257fcc07cbfa8adf59730f5810c4e63e4d0c9cb69a28
Timestamp: 1704710892 Timestamp [UCT]: 2024-01-08 10:48:12 Age [y:d:h:m:s]: 01:049:12:21:22
Block: 930792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296461 RingCT/type: yes/0
Extra: 01636ef708c42a75c36cd8257fcc07cbfa8adf59730f5810c4e63e4d0c9cb69a2802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd102b7f1a69ce3009574f16be95cdfad3b49b1746229e9f5148a44daf9326f0 0.600000000000 1388680 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": 930802, "vin": [ { "gen": { "height": 930792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd102b7f1a69ce3009574f16be95cdfad3b49b1746229e9f5148a44daf9326f0" } } ], "extra": [ 1, 99, 110, 247, 8, 196, 42, 117, 195, 108, 216, 37, 127, 204, 7, 203, 250, 138, 223, 89, 115, 15, 88, 16, 196, 230, 62, 77, 12, 156, 182, 154, 40, 2, 17, 0, 0, 0, 2, 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