Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6f006b6be056f0b3a61bb09fb0cc7ed2d291ea3ac87adc08a1891b87bd42e6f

Tx prefix hash: f734ba0aa71e301b139fa45509478adfd3792d46b3e75abbe800e5164cd32701
Tx public key: 414fedcdc12ba8ae6547ab898184f9f2c46cc2f43ed81336b9f117da0387d137
Timestamp: 1706805475 Timestamp [UCT]: 2024-02-01 16:37:55 Age [y:d:h:m:s]: 01:309:06:31:14
Block: 948148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479867 RingCT/type: yes/0
Extra: 01414fedcdc12ba8ae6547ab898184f9f2c46cc2f43ed81336b9f117da0387d13702110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66aa0566f0b6f318e1055724d70d32c072b53d3d7d9785a8846b9f4244cd8bf8 0.600000000000 1406520 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": 948158, "vin": [ { "gen": { "height": 948148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66aa0566f0b6f318e1055724d70d32c072b53d3d7d9785a8846b9f4244cd8bf8" } } ], "extra": [ 1, 65, 79, 237, 205, 193, 43, 168, 174, 101, 71, 171, 137, 129, 132, 249, 242, 196, 108, 194, 244, 62, 216, 19, 54, 185, 241, 23, 218, 3, 135, 209, 55, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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