Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bb383e84acad7b602b81e9c043096f0054f2c3156b112c7ade0daa75540ad6e

Tx prefix hash: 25ad2c371364d7db180a69144d35966ec7ef9ff38dbc94b87c40a3d7a028c05d
Tx public key: 0c81b4182f4b16a14539ea71b221fa8d03aeac7491ae5cef808bd2e81a11c836
Timestamp: 1727664553 Timestamp [UCT]: 2024-09-30 02:49:13 Age [y:d:h:m:s]: 00:237:06:41:07
Block: 1121096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169433 RingCT/type: yes/0
Extra: 010c81b4182f4b16a14539ea71b221fa8d03aeac7491ae5cef808bd2e81a11c83602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fccdb6de70a0ec0be032929710344e4cf8a2fbdc65229ba6e085c2aa62ba5f87 0.600000000000 1603247 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": 1121106, "vin": [ { "gen": { "height": 1121096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fccdb6de70a0ec0be032929710344e4cf8a2fbdc65229ba6e085c2aa62ba5f87" } } ], "extra": [ 1, 12, 129, 180, 24, 47, 75, 22, 161, 69, 57, 234, 113, 178, 33, 250, 141, 3, 174, 172, 116, 145, 174, 92, 239, 128, 139, 210, 232, 26, 17, 200, 54, 2, 17, 0, 0, 0, 4, 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