Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33366fc8a9c7cb93e04d4c846c754e13e684725ef71108e99a2e26a7f7ce607f

Tx prefix hash: fe43be5b8fe66e7cc317db9261abd3380b1fec819e6913c06bce2b8206ba9839
Tx public key: e99c939ac90a89c5fbbf1b4630584187871bbdac74cdaa2471a8151fbf7f4f89
Timestamp: 1721565832 Timestamp [UCT]: 2024-07-21 12:43:52 Age [y:d:h:m:s]: 01:109:11:54:40
Block: 1070528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336765 RingCT/type: yes/0
Extra: 01e99c939ac90a89c5fbbf1b4630584187871bbdac74cdaa2471a8151fbf7f4f89021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8894d14ca2f62ceb23189da69a7a94d7a75d5515f43f25011fdf4265c6aaf9d 0.600000000000 1542397 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": 1070538, "vin": [ { "gen": { "height": 1070528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8894d14ca2f62ceb23189da69a7a94d7a75d5515f43f25011fdf4265c6aaf9d" } } ], "extra": [ 1, 233, 156, 147, 154, 201, 10, 137, 197, 251, 191, 27, 70, 48, 88, 65, 135, 135, 27, 189, 172, 116, 205, 170, 36, 113, 168, 21, 31, 191, 127, 79, 137, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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