Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c3684f5a59dba23ec21c4d2169629cd4e2d3616133c5c6aae86e327111f7728

Tx prefix hash: ab19d641d32dda1d7e986342bdb64ce050f7cbd626723e4858a2746064f3a28f
Tx public key: 45e31c08f1015d65b7cd3d87251c3cc260f1c91ab3406f9a7acae908e972bc91
Timestamp: 1702697486 Timestamp [UCT]: 2023-12-16 03:31:26 Age [y:d:h:m:s]: 01:035:12:53:21
Block: 914108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286717 RingCT/type: yes/0
Extra: 0145e31c08f1015d65b7cd3d87251c3cc260f1c91ab3406f9a7acae908e972bc9102110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3600af57ff9b66be649aa9b5fed4f9171692fafb1b9f8715c2ee59ba778e26a2 0.600000000000 1371392 of 15

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": 914118, "vin": [ { "gen": { "height": 914108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3600af57ff9b66be649aa9b5fed4f9171692fafb1b9f8715c2ee59ba778e26a2" } } ], "extra": [ 1, 69, 227, 28, 8, 241, 1, 93, 101, 183, 205, 61, 135, 37, 28, 60, 194, 96, 241, 201, 26, 179, 64, 111, 154, 122, 202, 233, 8, 233, 114, 188, 145, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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