Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1426cf85067021ecc8447ec5970a30a0bbe63810431876ec3f88c277c6fcbd2

Tx prefix hash: a26a8818124afe4aacaa53742d0f9b628fb0664c24f3f24de0933d8a3b8ff09c
Tx public key: eb5e6ad9767741a4a4566303397dc94cd5a3c8bcd3bc816cbd1d96629a8db48d
Timestamp: 1705284035 Timestamp [UCT]: 2024-01-15 02:00:35 Age [y:d:h:m:s]: 01:043:19:00:22
Block: 935527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292381 RingCT/type: yes/0
Extra: 01eb5e6ad9767741a4a4566303397dc94cd5a3c8bcd3bc816cbd1d96629a8db48d021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 264cea8d161b32688efcae1e74a59fae1ba39bed9aeb74d1e5b81ddeb3a3fbf7 0.600000000000 1393543 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": 935537, "vin": [ { "gen": { "height": 935527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "264cea8d161b32688efcae1e74a59fae1ba39bed9aeb74d1e5b81ddeb3a3fbf7" } } ], "extra": [ 1, 235, 94, 106, 217, 118, 119, 65, 164, 164, 86, 99, 3, 57, 125, 201, 76, 213, 163, 200, 188, 211, 188, 129, 108, 189, 29, 150, 98, 154, 141, 180, 141, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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