Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb5995a6e849f3f591dc3a22230c037ce8a73a2b81cd8c47650f21cfef75c5dc

Tx prefix hash: dc5cc3793d84354ea8d9544dc75c9f246aa63c440debd4e5183df31b5a75ceaf
Tx public key: 7c47c24352f0d0a779e9a43f25fcf55d1bdd1e22151fcc390c493db0c282c581
Timestamp: 1706624274 Timestamp [UCT]: 2024-01-30 14:17:54 Age [y:d:h:m:s]: 01:069:02:13:30
Block: 946643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310462 RingCT/type: yes/0
Extra: 017c47c24352f0d0a779e9a43f25fcf55d1bdd1e22151fcc390c493db0c282c58102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a662494723d4a08666124a46d69b49263e2e1695a8ae1a6d3f0eda21f8f64e 0.600000000000 1404977 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": 946653, "vin": [ { "gen": { "height": 946643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a662494723d4a08666124a46d69b49263e2e1695a8ae1a6d3f0eda21f8f64e" } } ], "extra": [ 1, 124, 71, 194, 67, 82, 240, 208, 167, 121, 233, 164, 63, 37, 252, 245, 93, 27, 221, 30, 34, 21, 31, 204, 57, 12, 73, 61, 176, 194, 130, 197, 129, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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