Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3d2004cec20b167936fdc3c80db6ff21a2fad01ba35298d33be06260d6caa88

Tx prefix hash: 05bcbf17e0fc593c28a3ef3537e1d4cede419a7973a4c2d04a244a834317255b
Tx public key: e8977f610cb3e9f78095c5fff289604f675f6ef49c19a2a1372e1a4b4d84f2e3
Timestamp: 1700912192 Timestamp [UCT]: 2023-11-25 11:36:32 Age [y:d:h:m:s]: 01:055:12:39:27
Block: 899313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301033 RingCT/type: yes/0
Extra: 01e8977f610cb3e9f78095c5fff289604f675f6ef49c19a2a1372e1a4b4d84f2e3021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.642987741000 dcy

stealth address amount amount idx
00: 44922ee249cbfe438c68d3e66d05687bf82767af84eec6ce88d5deb8db51a39e 0.642987741000 1355760 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": 899323, "vin": [ { "gen": { "height": 899313 } } ], "vout": [ { "amount": 642987741, "target": { "key": "44922ee249cbfe438c68d3e66d05687bf82767af84eec6ce88d5deb8db51a39e" } } ], "extra": [ 1, 232, 151, 127, 97, 12, 179, 233, 247, 128, 149, 197, 255, 242, 137, 96, 79, 103, 95, 110, 244, 156, 25, 162, 161, 55, 46, 26, 75, 77, 132, 242, 227, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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