Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a9c9d65b93a6b51119a90800662de94f835cb9a961bf9204b12071b786b7f87

Tx prefix hash: 3c2f02c234a20e8483b9da690265fe60d49beeabd9bdeae3b73d73b4bfa86355
Tx public key: 41cfbc0ede8fc6a5b481e7a6b1fa9f0ee3f17d8d46d4c2ccd411cd8ce4a4afb9
Timestamp: 1710304414 Timestamp [UCT]: 2024-03-13 04:33:34 Age [y:d:h:m:s]: 00:298:21:04:04
Block: 977188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213942 RingCT/type: yes/0
Extra: 0141cfbc0ede8fc6a5b481e7a6b1fa9f0ee3f17d8d46d4c2ccd411cd8ce4a4afb902110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19b94be5b62e0c187168dc4730e92cc67e39db6e16a78b1c136ea00d1970003a 0.600000000000 1437189 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": 977198, "vin": [ { "gen": { "height": 977188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19b94be5b62e0c187168dc4730e92cc67e39db6e16a78b1c136ea00d1970003a" } } ], "extra": [ 1, 65, 207, 188, 14, 222, 143, 198, 165, 180, 129, 231, 166, 177, 250, 159, 14, 227, 241, 125, 141, 70, 212, 194, 204, 212, 17, 205, 140, 228, 164, 175, 185, 2, 17, 0, 0, 0, 9, 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