Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3035298d88f4f7e16a28f54be77536da30b2795d5775ddd32ee971012948413

Tx prefix hash: dae315b1e3ae83538b6203a106935808ec41961706a918e5a2a941c605f5d800
Tx public key: 46f7f10a41b7e7cadb8dd0a6c46de3284f9bf6a285e95f8c946139db0d998de9
Timestamp: 1725543248 Timestamp [UCT]: 2024-09-05 13:34:08 Age [y:d:h:m:s]: 01:064:23:02:13
Block: 1103521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304847 RingCT/type: yes/0
Extra: 0146f7f10a41b7e7cadb8dd0a6c46de3284f9bf6a285e95f8c946139db0d998de9021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d01a42ebce01def1d6ecd6e53a7eb1fc75a4ff10259c5973784169838d33e9b6 0.600000000000 1580380 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": 1103531, "vin": [ { "gen": { "height": 1103521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d01a42ebce01def1d6ecd6e53a7eb1fc75a4ff10259c5973784169838d33e9b6" } } ], "extra": [ 1, 70, 247, 241, 10, 65, 183, 231, 202, 219, 141, 208, 166, 196, 109, 227, 40, 79, 155, 246, 162, 133, 233, 95, 140, 148, 97, 57, 219, 13, 153, 141, 233, 2, 17, 0, 0, 0, 4, 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