Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f826fab0ad976101beb2ea09baa9e119aabafcfbdc7e9a45de8483fe82a6e38

Tx prefix hash: 3e0aa2aa79bf2edfe1ed0d62d4d00bfa3222ea2525deb235a5d1fb5db9e1f43d
Tx public key: c28d20736a0e2ac8ba336f1ccf7fd2c50cecc400e5ea559448a1832c6826cae7
Timestamp: 1580898161 Timestamp [UCT]: 2020-02-05 10:22:41 Age [y:d:h:m:s]: 05:072:11:29:07
Block: 59262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203724 RingCT/type: yes/0
Extra: 01c28d20736a0e2ac8ba336f1ccf7fd2c50cecc400e5ea559448a1832c6826cae702110000000d4ac5aa02000000000000000000

1 output(s) for total of 390.531630399000 dcy

stealth address amount amount idx
00: 673341644edc0b8ac80fd63e72c0a3475840c5507c1658348d5678b955afe0f2 390.531630399000 109392 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": 59272, "vin": [ { "gen": { "height": 59262 } } ], "vout": [ { "amount": 390531630399, "target": { "key": "673341644edc0b8ac80fd63e72c0a3475840c5507c1658348d5678b955afe0f2" } } ], "extra": [ 1, 194, 141, 32, 115, 106, 14, 42, 200, 186, 51, 111, 28, 207, 127, 210, 197, 12, 236, 196, 0, 229, 234, 85, 148, 72, 161, 131, 44, 104, 38, 202, 231, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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