Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 120bf937053480c39423e6eeb4b3af584cc015a3df45c2916ab39548b8982b73

Tx prefix hash: dd0cfa8b0c0e51c042edcbca2ac5a141286567462e41a3eff4c40213b4b9c11c
Tx public key: f79ea5701e3485c95bd7ee047128aa12ce72bb76fb512f28c1720abedcf27629
Timestamp: 1721094279 Timestamp [UCT]: 2024-07-16 01:44:39 Age [y:d:h:m:s]: 00:259:10:06:36
Block: 1066643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185308 RingCT/type: yes/0
Extra: 01f79ea5701e3485c95bd7ee047128aa12ce72bb76fb512f28c1720abedcf27629021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dff9a6bbb56cf6ade533f93bf841ffc14e7f3e0dea4433b1ead1d79c45993ba 0.600000000000 1537310 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": 1066653, "vin": [ { "gen": { "height": 1066643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dff9a6bbb56cf6ade533f93bf841ffc14e7f3e0dea4433b1ead1d79c45993ba" } } ], "extra": [ 1, 247, 158, 165, 112, 30, 52, 133, 201, 91, 215, 238, 4, 113, 40, 170, 18, 206, 114, 187, 118, 251, 81, 47, 40, 193, 114, 10, 190, 220, 242, 118, 41, 2, 17, 0, 0, 0, 7, 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