Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7168851d87a4ec34cf25e2bac79d84bcff1b998287dad8a946a1be36c879e63

Tx prefix hash: 289f5d3666f5920046eb62da9e817a361b0d273c2f7f3cd69cdc2b765bc3ff0b
Tx public key: e9e4c8a3cc9d953fb3ccfbea1f6e4892417913397af2676d884a13fbf38af70d
Timestamp: 1682344314 Timestamp [UCT]: 2023-04-24 13:51:54 Age [y:d:h:m:s]: 02:035:12:40:10
Block: 745615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547566 RingCT/type: yes/0
Extra: 01e9e4c8a3cc9d953fb3ccfbea1f6e4892417913397af2676d884a13fbf38af70d021100000003b3164c24000000000000000000

1 output(s) for total of 2.077151603000 dcy

stealth address amount amount idx
00: 08de149073e4c115aecddc2018d14b1dde3f041feec6c66483255d6b2ba7839c 2.077151603000 1193082 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": 745625, "vin": [ { "gen": { "height": 745615 } } ], "vout": [ { "amount": 2077151603, "target": { "key": "08de149073e4c115aecddc2018d14b1dde3f041feec6c66483255d6b2ba7839c" } } ], "extra": [ 1, 233, 228, 200, 163, 204, 157, 149, 63, 179, 204, 251, 234, 31, 110, 72, 146, 65, 121, 19, 57, 122, 242, 103, 109, 136, 74, 19, 251, 243, 138, 247, 13, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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