Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2b578606c1559b18f8f6b09758ef6a694cdea828373788ebb217a1d0c644930

Tx prefix hash: dcaec510082bab7b8c06267aec0ada7f43b00c17c6dec9706759fc833e037ba5
Tx public key: a96f51caf85238a47e1c8e0b0ac5a0ba2704b688ead98a40c95b2755c84371f3
Timestamp: 1724708347 Timestamp [UCT]: 2024-08-26 21:39:07 Age [y:d:h:m:s]: 00:292:13:28:03
Block: 1096573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208911 RingCT/type: yes/0
Extra: 01a96f51caf85238a47e1c8e0b0ac5a0ba2704b688ead98a40c95b2755c84371f3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87744bcdde043b493fe9aec5a7fc6129627492349e6c7485fe40342b86b6e6b5 0.600000000000 1571764 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": 1096583, "vin": [ { "gen": { "height": 1096573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87744bcdde043b493fe9aec5a7fc6129627492349e6c7485fe40342b86b6e6b5" } } ], "extra": [ 1, 169, 111, 81, 202, 248, 82, 56, 164, 126, 28, 142, 11, 10, 197, 160, 186, 39, 4, 182, 136, 234, 217, 138, 64, 201, 91, 39, 85, 200, 67, 113, 243, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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