Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec312d16bdddfaa6f82ee39261951c8cf0b5d87ef4f18f2821637fb37f3b1abf

Tx prefix hash: 1c79241697cece399312e4f34edd7f45f494a437fda95e065a5ba3a1b5b33a26
Tx public key: a9a41106b91f46507c83ddb9c28ed17a57a7a3c6ddeace675ef4f1b7662059f7
Timestamp: 1730069490 Timestamp [UCT]: 2024-10-27 22:51:30 Age [y:d:h:m:s]: 00:170:03:07:45
Block: 1140989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121415 RingCT/type: yes/0
Extra: 01a9a41106b91f46507c83ddb9c28ed17a57a7a3c6ddeace675ef4f1b7662059f70211000000058368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe6e36e78c8e01f7169b7dfd234999fd92e1a2e6885ce54503c14b8138699e30 0.600000000000 1624796 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": 1140999, "vin": [ { "gen": { "height": 1140989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe6e36e78c8e01f7169b7dfd234999fd92e1a2e6885ce54503c14b8138699e30" } } ], "extra": [ 1, 169, 164, 17, 6, 185, 31, 70, 80, 124, 131, 221, 185, 194, 142, 209, 122, 87, 167, 163, 198, 221, 234, 206, 103, 94, 244, 241, 183, 102, 32, 89, 247, 2, 17, 0, 0, 0, 5, 131, 104, 38, 109, 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