Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba2ee48dea9f69b7d8f22618716d57fbb299b7f4ca35db2b7746018968361420

Tx prefix hash: 7ddbea7ab9917977068a55e4ceeb64ac1f5ad2af78dbfe76653db57fd2227cd0
Tx public key: de1de87cb6ae851f6a6900e8e8457ea33c0cdcd4450639e0288b5ba00a4e9786
Timestamp: 1711342683 Timestamp [UCT]: 2024-03-25 04:58:03 Age [y:d:h:m:s]: 01:228:05:51:14
Block: 985804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421790 RingCT/type: yes/0
Extra: 01de1de87cb6ae851f6a6900e8e8457ea33c0cdcd4450639e0288b5ba00a4e97860211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b390094e9007e8430e8c46ad5e6c29ac7a4b250f09165a110512aa3f35facab 0.600000000000 1446023 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": 985814, "vin": [ { "gen": { "height": 985804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b390094e9007e8430e8c46ad5e6c29ac7a4b250f09165a110512aa3f35facab" } } ], "extra": [ 1, 222, 29, 232, 124, 182, 174, 133, 31, 106, 105, 0, 232, 232, 69, 126, 163, 60, 12, 220, 212, 69, 6, 57, 224, 40, 139, 91, 160, 10, 78, 151, 134, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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