Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ad25b0fc137706b015da7e67a7b23c01a813785d5627dfe68e0f23fe97d31ee

Tx prefix hash: a28a3954b6f45fd671b07546cea33c890a383145ad9462ea90191a6d3c373813
Tx public key: b0862a9a858d39aa74e0b727412902882dccf22a5cc8b54561e8a8112fb3fe12
Timestamp: 1735388650 Timestamp [UCT]: 2024-12-28 12:24:10 Age [y:d:h:m:s]: 00:079:21:37:56
Block: 1185005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56903 RingCT/type: yes/0
Extra: 01b0862a9a858d39aa74e0b727412902882dccf22a5cc8b54561e8a8112fb3fe120211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5d554d004bfcf341d04888470d22d4926c72e341a944ca897915ab00e142e5a 0.600000000000 1671470 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": 1185015, "vin": [ { "gen": { "height": 1185005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5d554d004bfcf341d04888470d22d4926c72e341a944ca897915ab00e142e5a" } } ], "extra": [ 1, 176, 134, 42, 154, 133, 141, 57, 170, 116, 224, 183, 39, 65, 41, 2, 136, 45, 204, 242, 42, 92, 200, 181, 69, 97, 232, 168, 17, 47, 179, 254, 18, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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