Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 825cb5fbd56c5e93c21c7c2427aa7d8f98772262640abaa96216f43a39be2f6f

Tx prefix hash: 96a00551c765a68de14939f472e0190521109697d50f62e9f52d8e841faf4bde
Tx public key: 587ff8622cf595e82813b9dc94692251b9c72ebc40d22b5e41f4771ed817b06f
Timestamp: 1727507913 Timestamp [UCT]: 2024-09-28 07:18:33 Age [y:d:h:m:s]: 00:170:05:20:37
Block: 1119810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121464 RingCT/type: yes/0
Extra: 01587ff8622cf595e82813b9dc94692251b9c72ebc40d22b5e41f4771ed817b06f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96b88fb9f4f258a35014c6374244bea1f2a7af29992b8d84ec97de63b0b1e198 0.600000000000 1601501 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": 1119820, "vin": [ { "gen": { "height": 1119810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96b88fb9f4f258a35014c6374244bea1f2a7af29992b8d84ec97de63b0b1e198" } } ], "extra": [ 1, 88, 127, 248, 98, 44, 245, 149, 232, 40, 19, 185, 220, 148, 105, 34, 81, 185, 199, 46, 188, 64, 210, 43, 94, 65, 244, 119, 30, 216, 23, 176, 111, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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