Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04dbd17cbc81b433f1f318b87086085ffce56e35ce3a0586eb4cda927cf14fb3

Tx prefix hash: d5772e9d3813f78bc9e759f879738e4df46d9bed709c7e6d9687ad0228fbc557
Tx public key: c7ee210f25e81fd4d8d95b8c758a69120025f779319bc6205cb0dac3ac743439
Timestamp: 1719494658 Timestamp [UCT]: 2024-06-27 13:24:18 Age [y:d:h:m:s]: 01:133:07:25:49
Block: 1053361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353822 RingCT/type: yes/0
Extra: 01c7ee210f25e81fd4d8d95b8c758a69120025f779319bc6205cb0dac3ac74343902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83b1fcc267d7900fc9757d817eb254f349c7fc7f5a0b274d143d4622d01fb1ba 0.600000000000 1523708 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": 1053371, "vin": [ { "gen": { "height": 1053361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83b1fcc267d7900fc9757d817eb254f349c7fc7f5a0b274d143d4622d01fb1ba" } } ], "extra": [ 1, 199, 238, 33, 15, 37, 232, 31, 212, 216, 217, 91, 140, 117, 138, 105, 18, 0, 37, 247, 121, 49, 155, 198, 32, 92, 176, 218, 195, 172, 116, 52, 57, 2, 17, 0, 0, 0, 4, 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