Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1aae20560fa22071f8d709ef32515d0780598b80936c114c1cf4464d8b587c6

Tx prefix hash: aa31e35f943a8f1c83db7868417944b5df9a45a2d32200db49e1f70657f5d992
Tx public key: c3415c4d4d18d025a01663ca0567d1e267fe0ba637e670e54c9059be8aa64b25
Timestamp: 1728663810 Timestamp [UCT]: 2024-10-11 16:23:30 Age [y:d:h:m:s]: 00:102:08:47:27
Block: 1129379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73135 RingCT/type: yes/0
Extra: 01c3415c4d4d18d025a01663ca0567d1e267fe0ba637e670e54c9059be8aa64b25021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf47ee65e8ab64520609850211fbfe4ee877bef5fb36642049c3eb8a5ba385f2 0.600000000000 1612204 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": 1129389, "vin": [ { "gen": { "height": 1129379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf47ee65e8ab64520609850211fbfe4ee877bef5fb36642049c3eb8a5ba385f2" } } ], "extra": [ 1, 195, 65, 92, 77, 77, 24, 208, 37, 160, 22, 99, 202, 5, 103, 209, 226, 103, 254, 11, 166, 55, 230, 112, 229, 76, 144, 89, 190, 138, 166, 75, 37, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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