Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2480b80a6323840ebe903cf9c2c5d82e9627317b059d4e412bce95b3e7524e2

Tx prefix hash: 5bf2efd01f5236105e9838870aac86707d4727bec2ef34a159ba205d19839010
Tx public key: ba6c07a349d07266313dc450813c290f401cae3aa793e81b5bbbfb05b87614aa
Timestamp: 1708695661 Timestamp [UCT]: 2024-02-23 13:41:01 Age [y:d:h:m:s]: 01:270:17:29:14
Block: 963837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452237 RingCT/type: yes/0
Extra: 01ba6c07a349d07266313dc450813c290f401cae3aa793e81b5bbbfb05b87614aa0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eae10e24998225a95100d8c802e8797c8d47efbdb8fd4d2c39dd6f1e2ac730fc 0.600000000000 1423564 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": 963847, "vin": [ { "gen": { "height": 963837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eae10e24998225a95100d8c802e8797c8d47efbdb8fd4d2c39dd6f1e2ac730fc" } } ], "extra": [ 1, 186, 108, 7, 163, 73, 208, 114, 102, 49, 61, 196, 80, 129, 60, 41, 15, 64, 28, 174, 58, 167, 147, 232, 27, 91, 187, 251, 5, 184, 118, 20, 170, 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