Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f10101a197bf10f5292eb598a913e7acd530e4198ce16761cfd7f50e1f6c8bb5

Tx prefix hash: 99b2a5ee37665e13266c7790d849da1ed034c3d92805f49e318c6abc9075443b
Tx public key: 2c0cb388ad30e7800d6557a12e54e80b844286fc893e83336656d11ef2f39f71
Timestamp: 1715791385 Timestamp [UCT]: 2024-05-15 16:43:05 Age [y:d:h:m:s]: 00:331:06:11:21
Block: 1022658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236788 RingCT/type: yes/0
Extra: 012c0cb388ad30e7800d6557a12e54e80b844286fc893e83336656d11ef2f39f71021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 060f17a2cccf0f092a9fc7543ce4f3bc626c4a1ef9e572c398008d3f8fe52610 0.600000000000 1487327 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": 1022668, "vin": [ { "gen": { "height": 1022658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "060f17a2cccf0f092a9fc7543ce4f3bc626c4a1ef9e572c398008d3f8fe52610" } } ], "extra": [ 1, 44, 12, 179, 136, 173, 48, 231, 128, 13, 101, 87, 161, 46, 84, 232, 11, 132, 66, 134, 252, 137, 62, 131, 51, 102, 86, 209, 30, 242, 243, 159, 113, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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