Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ed59969b97b490968b49f3caaf765cb4acbe032e4d845f39c6eaf2efb387d1a

Tx prefix hash: 2745386f463fe5097ec91f8a40b1ab502d6cc9ae59dc0e9c5726d5e3755f3354
Tx public key: fb06657077bf99e0d769ae94452692bbc1eb3a65f67b18d5f8ddb90e73fecc97
Timestamp: 1704070193 Timestamp [UCT]: 2024-01-01 00:49:53 Age [y:d:h:m:s]: 01:117:11:31:59
Block: 925485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345096 RingCT/type: yes/0
Extra: 01fb06657077bf99e0d769ae94452692bbc1eb3a65f67b18d5f8ddb90e73fecc97021100000002ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1710cff8aed51443a41e6526bc5030747676f5b8039602ac7020554dc1d9440b 0.600000000000 1383249 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": 925495, "vin": [ { "gen": { "height": 925485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1710cff8aed51443a41e6526bc5030747676f5b8039602ac7020554dc1d9440b" } } ], "extra": [ 1, 251, 6, 101, 112, 119, 191, 153, 224, 215, 105, 174, 148, 69, 38, 146, 187, 193, 235, 58, 101, 246, 123, 24, 213, 248, 221, 185, 14, 115, 254, 204, 151, 2, 17, 0, 0, 0, 2, 172, 50, 141, 17, 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