Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb431bfbf7ad27abd16dbd7d659bcfc77b01c6d4764427f3228d4758e015d5a4

Tx prefix hash: 116308417054e3708200ae4c2ec7fb7cb6a529d329e4e4d0f8e319536a26dae4
Tx public key: cc8b254c827699f0eb7fe3db7aaa1128b0f863487105b518259e4004f9ccb406
Timestamp: 1724905844 Timestamp [UCT]: 2024-08-29 04:30:44 Age [y:d:h:m:s]: 00:223:23:03:50
Block: 1098225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159927 RingCT/type: yes/0
Extra: 01cc8b254c827699f0eb7fe3db7aaa1128b0f863487105b518259e4004f9ccb40602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da81270aab616c933379abdaf3d0175d0b31feda026343a636c9d69e4e5f1ab5 0.600000000000 1573868 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": 1098235, "vin": [ { "gen": { "height": 1098225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da81270aab616c933379abdaf3d0175d0b31feda026343a636c9d69e4e5f1ab5" } } ], "extra": [ 1, 204, 139, 37, 76, 130, 118, 153, 240, 235, 127, 227, 219, 122, 170, 17, 40, 176, 248, 99, 72, 113, 5, 181, 24, 37, 158, 64, 4, 249, 204, 180, 6, 2, 17, 0, 0, 0, 1, 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