Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 497fa1dc811c952c1c10abb7dfec648b2ddfa4681b83c6b3fcb60d72fa68c2cd

Tx prefix hash: 2212c383dfa6d570fa98900562d11d66047b22fd71ed98dfabd93eae671138e0
Tx public key: 9f52da148781b0b7b1ab2a450582b5e1f28ef4812fc5aa21776ab079463f98be
Timestamp: 1737804492 Timestamp [UCT]: 2025-01-25 11:28:12 Age [y:d:h:m:s]: 00:290:23:29:45
Block: 1204968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205494 RingCT/type: yes/0
Extra: 019f52da148781b0b7b1ab2a450582b5e1f28ef4812fc5aa21776ab079463f98be021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90a7c817d9ca021db916f9f8c19f22038dfb3e9e3765ed1cfbaf456de88f1e95 0.600000000000 1691663 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": 1204978, "vin": [ { "gen": { "height": 1204968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90a7c817d9ca021db916f9f8c19f22038dfb3e9e3765ed1cfbaf456de88f1e95" } } ], "extra": [ 1, 159, 82, 218, 20, 135, 129, 176, 183, 177, 171, 42, 69, 5, 130, 181, 225, 242, 142, 244, 129, 47, 197, 170, 33, 119, 106, 176, 121, 70, 63, 152, 190, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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