Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 185f1160736c9ba7ac656843c7559a5f6dd6d4986dee8208896886f424d2a371

Tx prefix hash: 898fa2bf611395e74504c22ee71a9f3f85b6e50fae834a361b1e6a633fc4480e
Tx public key: e1d2969c9dcba6f4d6db7158436277c05f06abcb12f2eb5b7a8d6ca2b5a6699a
Timestamp: 1724101659 Timestamp [UCT]: 2024-08-19 21:07:39 Age [y:d:h:m:s]: 00:227:05:05:03
Block: 1091562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162246 RingCT/type: yes/0
Extra: 01e1d2969c9dcba6f4d6db7158436277c05f06abcb12f2eb5b7a8d6ca2b5a6699a02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 573db250324b5015d336e7ecda0e892ed923f2d234e61d89372f5f16fca423be 0.600000000000 1566195 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": 1091572, "vin": [ { "gen": { "height": 1091562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "573db250324b5015d336e7ecda0e892ed923f2d234e61d89372f5f16fca423be" } } ], "extra": [ 1, 225, 210, 150, 156, 157, 203, 166, 244, 214, 219, 113, 88, 67, 98, 119, 192, 95, 6, 171, 203, 18, 242, 235, 91, 122, 141, 108, 162, 181, 166, 105, 154, 2, 17, 0, 0, 0, 6, 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