Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea007e69f3cf5548539a458cd7b9ac2d8b2ec96c5db77d1e7bcd1431049aacce

Tx prefix hash: 35be15a9250f48a0b8c32af096bbf5c91e0c8365362de26bfce80f1188469e4d
Tx public key: 787ce4b38cedd220105704429d15c1b3fb2549271ccd2dc01f1b81acb4a55878
Timestamp: 1704789137 Timestamp [UCT]: 2024-01-09 08:32:17 Age [y:d:h:m:s]: 01:089:09:00:43
Block: 931436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324974 RingCT/type: yes/0
Extra: 01787ce4b38cedd220105704429d15c1b3fb2549271ccd2dc01f1b81acb4a558780211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b3ae1efc52696db7099425152c1c74c4dead4240c2dcbe7c6f0fda8660af9b8 0.600000000000 1389334 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": 931446, "vin": [ { "gen": { "height": 931436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b3ae1efc52696db7099425152c1c74c4dead4240c2dcbe7c6f0fda8660af9b8" } } ], "extra": [ 1, 120, 124, 228, 179, 140, 237, 210, 32, 16, 87, 4, 66, 157, 21, 193, 179, 251, 37, 73, 39, 28, 205, 45, 192, 31, 27, 129, 172, 180, 165, 88, 120, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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