Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a7cac1b468103cadeab5f84d877219632e7e02c5fca9c99eee37eb29d58843d

Tx prefix hash: 18cf9b80af4a4ce1f54f430734b86d6910b03aa635e547f319c3646e88ca2b11
Tx public key: 4e03ad7f92b02b9ff5c0bcfdaaa64374edb57da45b874429b08b71e51b6e8865
Timestamp: 1706737712 Timestamp [UCT]: 2024-01-31 21:48:32 Age [y:d:h:m:s]: 01:060:02:43:26
Block: 947586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304038 RingCT/type: yes/0
Extra: 014e03ad7f92b02b9ff5c0bcfdaaa64374edb57da45b874429b08b71e51b6e886502110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02439cac188fbae41b0fb6732ba3581be0761a9a827f3ed43adc7aff6fedd293 0.600000000000 1405938 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": 947596, "vin": [ { "gen": { "height": 947586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02439cac188fbae41b0fb6732ba3581be0761a9a827f3ed43adc7aff6fedd293" } } ], "extra": [ 1, 78, 3, 173, 127, 146, 176, 43, 159, 245, 192, 188, 253, 170, 166, 67, 116, 237, 181, 125, 164, 91, 135, 68, 41, 176, 139, 113, 229, 27, 110, 136, 101, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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