Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 959630363709616e3c04868d16dfdfbdbd60e0d18ef7ace4e63aac506d03b3cc

Tx prefix hash: ff05b12e88979844035d4a93efc923e20847132a660fea0f32bb1f24749c6b60
Tx public key: 61250cbfe3eb1b5e9e46b76434d2dc7434d7335dc4b8393c7ec1b43561ca3b4a
Timestamp: 1716861594 Timestamp [UCT]: 2024-05-28 01:59:54 Age [y:d:h:m:s]: 00:291:04:05:26
Block: 1031554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208090 RingCT/type: yes/0
Extra: 0161250cbfe3eb1b5e9e46b76434d2dc7434d7335dc4b8393c7ec1b43561ca3b4a021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcb752a42c452d1979b1cae1fed0d75392e08fce6b2112da1359d160dbc1a056 0.600000000000 1500003 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": 1031564, "vin": [ { "gen": { "height": 1031554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcb752a42c452d1979b1cae1fed0d75392e08fce6b2112da1359d160dbc1a056" } } ], "extra": [ 1, 97, 37, 12, 191, 227, 235, 27, 94, 158, 70, 183, 100, 52, 210, 220, 116, 52, 215, 51, 93, 196, 184, 57, 60, 126, 193, 180, 53, 97, 202, 59, 74, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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