Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 129f2fbfdc4ff87237e5305ecbaa3d08749f3380673fc8afc7d4a4116467a2cb

Tx prefix hash: 036a9f560194100173f9099aad2c434dcad7a0c62ab8f872af2a8f60dfdb25da
Tx public key: 673fd813642a55a63313bb081c4d8d912baf6719474b79ef0d4a745bbe5da00a
Timestamp: 1737019718 Timestamp [UCT]: 2025-01-16 09:28:38 Age [y:d:h:m:s]: 00:152:03:11:32
Block: 1198506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108454 RingCT/type: yes/0
Extra: 01673fd813642a55a63313bb081c4d8d912baf6719474b79ef0d4a745bbe5da00a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31e4c125aef56d35c6b6e6c6d7534d3bb12acf0f4b29b2abc7757b01ead9c65e 0.600000000000 1685131 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": 1198516, "vin": [ { "gen": { "height": 1198506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31e4c125aef56d35c6b6e6c6d7534d3bb12acf0f4b29b2abc7757b01ead9c65e" } } ], "extra": [ 1, 103, 63, 216, 19, 100, 42, 85, 166, 51, 19, 187, 8, 28, 77, 141, 145, 43, 175, 103, 25, 71, 75, 121, 239, 13, 74, 116, 91, 190, 93, 160, 10, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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