Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed70d3e1aad82b09e10a8339b421db3b7f165ec841208bd546884d448460840e

Tx prefix hash: bb5fce9e0d47733f69d659dc919620b902227d3cc46e002792e1eda968f79812
Tx public key: 1eac3e403f4d25bc8018a0766ab140f2f341afe757b2c77d902450c1aa4baaf9
Timestamp: 1730672199 Timestamp [UCT]: 2024-11-03 22:16:39 Age [y:d:h:m:s]: 00:020:06:11:00
Block: 1145947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14498 RingCT/type: yes/0
Extra: 011eac3e403f4d25bc8018a0766ab140f2f341afe757b2c77d902450c1aa4baaf90211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d723f7853881e1e57dfda8da22794293b263f204bc3aa7b8f83deb33e5dc508 0.600000000000 1630480 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": 1145957, "vin": [ { "gen": { "height": 1145947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d723f7853881e1e57dfda8da22794293b263f204bc3aa7b8f83deb33e5dc508" } } ], "extra": [ 1, 30, 172, 62, 64, 63, 77, 37, 188, 128, 24, 160, 118, 106, 177, 64, 242, 243, 65, 175, 231, 87, 178, 199, 125, 144, 36, 80, 193, 170, 75, 170, 249, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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