Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07bef99a456801228cd0faecbfe6dfaecbc7001c1a2b4473275201f515801ea1

Tx prefix hash: 7fa02b73462b57b7d8bcd656c2bb1c75d73ea18e94df9aabfe16651a4f29621b
Tx public key: 8ac7378a303e8fb357fd6f8525f3a675dfee1075bf3b349022cabf97d13df86a
Timestamp: 1705030277 Timestamp [UCT]: 2024-01-12 03:31:17 Age [y:d:h:m:s]: 01:045:13:55:46
Block: 933431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293653 RingCT/type: yes/0
Extra: 018ac7378a303e8fb357fd6f8525f3a675dfee1075bf3b349022cabf97d13df86a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3eacbab2caeafc625338497b7e7fc2f7d8b19978ef14c9b724c99d443889b157 0.600000000000 1391393 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": 933441, "vin": [ { "gen": { "height": 933431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3eacbab2caeafc625338497b7e7fc2f7d8b19978ef14c9b724c99d443889b157" } } ], "extra": [ 1, 138, 199, 55, 138, 48, 62, 143, 179, 87, 253, 111, 133, 37, 243, 166, 117, 223, 238, 16, 117, 191, 59, 52, 144, 34, 202, 191, 151, 209, 61, 248, 106, 2, 17, 0, 0, 0, 1, 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