Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f308e91a3750acb030d7a3df8dd22ce0afaea305f140d5f5cb34844bba42cf85

Tx prefix hash: d1f531de2eb2bdaac2044564fcf257b729aac57fcca5d16eaeb11d6f4bb84012
Tx public key: 0ad1a1a7967a413de571e828448b91558d993f07cd41982e6b5ef4394badc2aa
Timestamp: 1714807675 Timestamp [UCT]: 2024-05-04 07:27:55 Age [y:d:h:m:s]: 00:248:07:21:42
Block: 1014515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177724 RingCT/type: yes/0
Extra: 010ad1a1a7967a413de571e828448b91558d993f07cd41982e6b5ef4394badc2aa0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 711e9147f24d1d66d71452ea9df3b4a044ece343ee53f5cfa2f96238fe5349d1 0.600000000000 1477628 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": 1014525, "vin": [ { "gen": { "height": 1014515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "711e9147f24d1d66d71452ea9df3b4a044ece343ee53f5cfa2f96238fe5349d1" } } ], "extra": [ 1, 10, 209, 161, 167, 150, 122, 65, 61, 229, 113, 232, 40, 68, 139, 145, 85, 141, 153, 63, 7, 205, 65, 152, 46, 107, 94, 244, 57, 75, 173, 194, 170, 2, 17, 0, 0, 0, 3, 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