Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2656e464945e904c7b0bb9d3710354655bd59e4d0b7d3b9a9fce4963cc04d81

Tx prefix hash: 667e19082af98de3648e169984d791a552c1add5bfe6576087058f11ed73decd
Tx public key: 9bc9a504a281e126b6bd88debfa6cde243b9e63e77c2a500cfeda6259a654f6b
Timestamp: 1577676415 Timestamp [UCT]: 2019-12-30 03:26:55 Age [y:d:h:m:s]: 05:034:22:38:02
Block: 34752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174717 RingCT/type: yes/0
Extra: 019bc9a504a281e126b6bd88debfa6cde243b9e63e77c2a500cfeda6259a654f6b02110000000f4ac5aa02000000000000000000

1 output(s) for total of 470.817994509000 dcy

stealth address amount amount idx
00: b36efc653a0507eb288262f5477c68cd64e6225a734e798038bdcea37e91a4d1 470.817994509000 58518 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": 34762, "vin": [ { "gen": { "height": 34752 } } ], "vout": [ { "amount": 470817994509, "target": { "key": "b36efc653a0507eb288262f5477c68cd64e6225a734e798038bdcea37e91a4d1" } } ], "extra": [ 1, 155, 201, 165, 4, 162, 129, 225, 38, 182, 189, 136, 222, 191, 166, 205, 226, 67, 185, 230, 62, 119, 194, 165, 0, 207, 237, 166, 37, 154, 101, 79, 107, 2, 17, 0, 0, 0, 15, 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