Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bea187a58ebb7776330321070a9ecf4ec40d6e6d881fb53b19f7e55ebadd8128

Tx prefix hash: 08a124a16340cddeb625ad0274a32ed471773462dc01b5a93f37a1ee331351dc
Tx public key: 244cd5cbaea62d8ed896095f4329b4ad565da69b0d48d5099ef26d03a03a25a8
Timestamp: 1721822784 Timestamp [UCT]: 2024-07-24 12:06:24 Age [y:d:h:m:s]: 00:279:00:24:54
Block: 1072657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199357 RingCT/type: yes/0
Extra: 01244cd5cbaea62d8ed896095f4329b4ad565da69b0d48d5099ef26d03a03a25a8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce301ea52e9816e56ca95890d9d3fb2b8f78fb3df6b6b28aa3823d3cba2e0007 0.600000000000 1545142 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": 1072667, "vin": [ { "gen": { "height": 1072657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce301ea52e9816e56ca95890d9d3fb2b8f78fb3df6b6b28aa3823d3cba2e0007" } } ], "extra": [ 1, 36, 76, 213, 203, 174, 166, 45, 142, 216, 150, 9, 95, 67, 41, 180, 173, 86, 93, 166, 155, 13, 72, 213, 9, 158, 242, 109, 3, 160, 58, 37, 168, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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