Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 023e0b8bec372c73c1d2ece186b782dc8967161d6c6e492106f65c828eaad742

Tx prefix hash: 49c2bc061d632c3122589e306e3a136c9a42d67596b525135fe4926d7cbf260b
Tx public key: ee45c4df132dd5ce8f7505b3ead3e7e394a6426cc4e5acd0b370f78068ccfb17
Timestamp: 1731188409 Timestamp [UCT]: 2024-11-09 21:40:09 Age [y:d:h:m:s]: 00:174:21:00:22
Block: 1150232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124819 RingCT/type: yes/0
Extra: 01ee45c4df132dd5ce8f7505b3ead3e7e394a6426cc4e5acd0b370f78068ccfb17021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac425e6ab7e91026d781a0fd7d9a169caeb7c8d289a51cc41ce111287c62010c 0.600000000000 1635481 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": 1150242, "vin": [ { "gen": { "height": 1150232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac425e6ab7e91026d781a0fd7d9a169caeb7c8d289a51cc41ce111287c62010c" } } ], "extra": [ 1, 238, 69, 196, 223, 19, 45, 213, 206, 143, 117, 5, 179, 234, 211, 231, 227, 148, 166, 66, 108, 196, 229, 172, 208, 179, 112, 247, 128, 104, 204, 251, 23, 2, 17, 0, 0, 0, 1, 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