Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b80bbc9cfa19f50039af5953ecd18dfc056504b8626c7041effda71b6e0a9223

Tx prefix hash: edb958a2520b693b4d5ab9950fa4cd668df57baa158fe62233fad5f6f2a5dab8
Tx public key: bb99d0aa77bf5aab788067e8e85b054fda32f4f8d7232bec0e074acdaab78c87
Timestamp: 1727796643 Timestamp [UCT]: 2024-10-01 15:30:43 Age [y:d:h:m:s]: 00:190:14:30:50
Block: 1122200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136023 RingCT/type: yes/0
Extra: 01bb99d0aa77bf5aab788067e8e85b054fda32f4f8d7232bec0e074acdaab78c8702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 175084eac5c912afd8d5e1bb0d643360a0cfa04940ecd4a34702dd7e36dc10d6 0.600000000000 1604607 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": 1122210, "vin": [ { "gen": { "height": 1122200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "175084eac5c912afd8d5e1bb0d643360a0cfa04940ecd4a34702dd7e36dc10d6" } } ], "extra": [ 1, 187, 153, 208, 170, 119, 191, 90, 171, 120, 128, 103, 232, 232, 91, 5, 79, 218, 50, 244, 248, 215, 35, 43, 236, 14, 7, 74, 205, 170, 183, 140, 135, 2, 17, 0, 0, 0, 5, 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