Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79aa162c2ab0047945849408350aa90355296c93402deea7fc097fb60a4ff59a

Tx prefix hash: da0474acba66558dd8ff5ad475866703a063d0e5cfd7f84348491fb4a5bae84b
Tx public key: e7aa3ea4b5da476f3f1d35617bcb6548242ae6ec0ce34350c636a26c5b344069
Timestamp: 1730682226 Timestamp [UCT]: 2024-11-04 01:03:46 Age [y:d:h:m:s]: 00:147:04:45:57
Block: 1146037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105024 RingCT/type: yes/0
Extra: 01e7aa3ea4b5da476f3f1d35617bcb6548242ae6ec0ce34350c636a26c5b3440690211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 671306368d545dcad3a6a886979d94cc4883709f834e2c299abf1a94cc4e27aa 0.600000000000 1630592 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": 1146047, "vin": [ { "gen": { "height": 1146037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "671306368d545dcad3a6a886979d94cc4883709f834e2c299abf1a94cc4e27aa" } } ], "extra": [ 1, 231, 170, 62, 164, 181, 218, 71, 111, 63, 29, 53, 97, 123, 203, 101, 72, 36, 42, 230, 236, 12, 227, 67, 80, 198, 54, 162, 108, 91, 52, 64, 105, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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