Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df4ad3e2dfc944307a9361147075d1d272747b70d938ec48a667a17b2d81e8da

Tx prefix hash: 8aece6c8ab2c8283bc42f9c6d18e14ffc202a2cc7a643bd54db03c80a19ff1cd
Tx public key: 002b6104886bad3515bd7c3e89428f772f4cc704b62ba6bee9a2af19fa2bcde1
Timestamp: 1715413838 Timestamp [UCT]: 2024-05-11 07:50:38 Age [y:d:h:m:s]: 00:333:20:24:39
Block: 1019560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238614 RingCT/type: yes/0
Extra: 01002b6104886bad3515bd7c3e89428f772f4cc704b62ba6bee9a2af19fa2bcde10211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e7575c03851a994c1367340ced4b28b669212e14f602f4a5f3b2f5fa064c25b 0.600000000000 1483561 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": 1019570, "vin": [ { "gen": { "height": 1019560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e7575c03851a994c1367340ced4b28b669212e14f602f4a5f3b2f5fa064c25b" } } ], "extra": [ 1, 0, 43, 97, 4, 136, 107, 173, 53, 21, 189, 124, 62, 137, 66, 143, 119, 47, 76, 199, 4, 182, 43, 166, 190, 233, 162, 175, 25, 250, 43, 205, 225, 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