Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fdc00d96f3059b908ab6710b95e4619cf8b1f6d0a2fc45206799f23a6b65e40

Tx prefix hash: 64f6ce5b6e85c6a210ed03b8b0e048de231eca56426e73187f10e75a5c178c0c
Tx public key: 8ee6e5accc75327e81988f2bfe6d023dc6a92bff5ac7c43113d7c1857fa28b91
Timestamp: 1648604818 Timestamp [UCT]: 2022-03-30 01:46:58 Age [y:d:h:m:s]: 02:234:07:54:04
Block: 469265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687042 RingCT/type: yes/0
Extra: 018ee6e5accc75327e81988f2bfe6d023dc6a92bff5ac7c43113d7c1857fa28b910211000000084a0f5013000000000000000000

1 output(s) for total of 17.105292475000 dcy

stealth address amount amount idx
00: aa4d4a1c860698096e6cb3a06694b917f01b784a6163fb2196a90ccfecbd1964 17.105292475000 888177 of 0

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": 469275, "vin": [ { "gen": { "height": 469265 } } ], "vout": [ { "amount": 17105292475, "target": { "key": "aa4d4a1c860698096e6cb3a06694b917f01b784a6163fb2196a90ccfecbd1964" } } ], "extra": [ 1, 142, 230, 229, 172, 204, 117, 50, 126, 129, 152, 143, 43, 254, 109, 2, 61, 198, 169, 43, 255, 90, 199, 196, 49, 19, 215, 193, 133, 127, 162, 139, 145, 2, 17, 0, 0, 0, 8, 74, 15, 80, 19, 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