Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4955475d3599f4afe553750e9fa0e3de9f2e93d92b52ad1e86421070c3d1b52d

Tx prefix hash: b7d1cb6cbeb0f27242e3ed4cbf25f57782e67bc250cf48753d5d07760cc8b85e
Tx public key: 0a45045df63c0e95455bb12c0fea9f1c20509bddb768d526eb623de951c204e3
Timestamp: 1743137163 Timestamp [UCT]: 2025-03-28 04:46:03 Age [y:d:h:m:s]: 00:255:07:15:40
Block: 1248886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180225 RingCT/type: yes/0
Extra: 010a45045df63c0e95455bb12c0fea9f1c20509bddb768d526eb623de951c204e3021100000005d2e40efd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c13b7450e41cc95a5e3c16d0469dfcf6092b364089778cbd821718fe1c4f125 0.600000000000 1735921 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": 1248896, "vin": [ { "gen": { "height": 1248886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c13b7450e41cc95a5e3c16d0469dfcf6092b364089778cbd821718fe1c4f125" } } ], "extra": [ 1, 10, 69, 4, 93, 246, 60, 14, 149, 69, 91, 177, 44, 15, 234, 159, 28, 32, 80, 155, 221, 183, 104, 213, 38, 235, 98, 61, 233, 81, 194, 4, 227, 2, 17, 0, 0, 0, 5, 210, 228, 14, 253, 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