Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bdbb577a3ca2474bb5feb37ff56ad95528297542b87c877b166a5a05f993b1a

Tx prefix hash: 6857ce983e174dc92a8a2381278c067b1e62f4fc8f9925d5e934d9ad7e6091cc
Tx public key: 991ad35a2ac361a8f1c55aafa3fd92e7745f519cf27737af0fd4740049fa5bc9
Timestamp: 1709400755 Timestamp [UCT]: 2024-03-02 17:32:35 Age [y:d:h:m:s]: 01:046:01:48:26
Block: 969694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293922 RingCT/type: yes/0
Extra: 01991ad35a2ac361a8f1c55aafa3fd92e7745f519cf27737af0fd4740049fa5bc902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4f2b7b55d68e121d1921c0a5a46e76f340167d81fb501e3c23f95f33852d036 0.600000000000 1429531 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": 969704, "vin": [ { "gen": { "height": 969694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4f2b7b55d68e121d1921c0a5a46e76f340167d81fb501e3c23f95f33852d036" } } ], "extra": [ 1, 153, 26, 211, 90, 42, 195, 97, 168, 241, 197, 90, 175, 163, 253, 146, 231, 116, 95, 81, 156, 242, 119, 55, 175, 15, 212, 116, 0, 73, 250, 91, 201, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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