Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca8df6496b4888bf88139b7bb207a403b93acc8745037dcddec8dc1f6bf80ce6

Tx prefix hash: b7098fe3ae3a96cf602f62c82c802fe28ef5a47b724a11a6249f197e4757ed88
Tx public key: 837c56c15907dbcf0364524989798a0b1748e1d440fe1eb50ad9b88eca8769a2
Timestamp: 1583931409 Timestamp [UCT]: 2020-03-11 12:56:49 Age [y:d:h:m:s]: 04:260:11:38:33
Block: 80409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1081350 RingCT/type: yes/0
Extra: 01837c56c15907dbcf0364524989798a0b1748e1d440fe1eb50ad9b88eca8769a2021100000004c48ea382000000000000000000

1 output(s) for total of 332.332177379000 dcy

stealth address amount amount idx
00: 10a471a0b59c6accbc055c0e645f923524f3c9a1352efd4c4e89f9b014e81e4b 332.332177379000 147181 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": 80419, "vin": [ { "gen": { "height": 80409 } } ], "vout": [ { "amount": 332332177379, "target": { "key": "10a471a0b59c6accbc055c0e645f923524f3c9a1352efd4c4e89f9b014e81e4b" } } ], "extra": [ 1, 131, 124, 86, 193, 89, 7, 219, 207, 3, 100, 82, 73, 137, 121, 138, 11, 23, 72, 225, 212, 64, 254, 30, 181, 10, 217, 184, 142, 202, 135, 105, 162, 2, 17, 0, 0, 0, 4, 196, 142, 163, 130, 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