Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fffc3aa6037190b28b415b66f3b5ee5e1d668f59e7ad2acc06cbd3fdb66b5ca

Tx prefix hash: 165505e1dfe67c1a3f258215911d6e60241ed0dca8d48932d0acd34322bd215d
Tx public key: 28a8e8a7241ca668dfffac4ff588616b1c77769e260307873d67bb6aa5226060
Timestamp: 1686326620 Timestamp [UCT]: 2023-06-09 16:03:40 Age [y:d:h:m:s]: 02:007:23:16:17
Block: 778647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527677 RingCT/type: yes/0
Extra: 0128a8e8a7241ca668dfffac4ff588616b1c77769e260307873d67bb6aa522606002110000000a75e3f0e9000000000000000000

1 output(s) for total of 1.614430741000 dcy

stealth address amount amount idx
00: db575bc218a89e199aecc131d46e4afd4bef928b2bb8617349b5e950d8beab84 1.614430741000 1228282 of 0

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": 778657, "vin": [ { "gen": { "height": 778647 } } ], "vout": [ { "amount": 1614430741, "target": { "key": "db575bc218a89e199aecc131d46e4afd4bef928b2bb8617349b5e950d8beab84" } } ], "extra": [ 1, 40, 168, 232, 167, 36, 28, 166, 104, 223, 255, 172, 79, 245, 136, 97, 107, 28, 119, 118, 158, 38, 3, 7, 135, 61, 103, 187, 106, 165, 34, 96, 96, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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