Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fba20a4cb654acdcf5b094e1af37156348831f57c37b9ebeac4b5202cbe81a7d

Tx prefix hash: b5a69f1b0995336313028e6fa1c08a2c013f9988e68a82d438531cb08c11e6df
Tx public key: 50c3f34cc482d8824dece7baf761328afec5768d5106288f75ade4393e6ef79f
Timestamp: 1707150222 Timestamp [UCT]: 2024-02-05 16:23:42 Age [y:d:h:m:s]: 01:131:11:09:38
Block: 951011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354967 RingCT/type: yes/0
Extra: 0150c3f34cc482d8824dece7baf761328afec5768d5106288f75ade4393e6ef79f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be99ae9e7d9828f79b7dc53cb98f12d3c0fb6c62538ff6d8da84076a1fa2c442 0.600000000000 1409713 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": 951021, "vin": [ { "gen": { "height": 951011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be99ae9e7d9828f79b7dc53cb98f12d3c0fb6c62538ff6d8da84076a1fa2c442" } } ], "extra": [ 1, 80, 195, 243, 76, 196, 130, 216, 130, 77, 236, 231, 186, 247, 97, 50, 138, 254, 197, 118, 141, 81, 6, 40, 143, 117, 173, 228, 57, 62, 110, 247, 159, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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