Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcefe96f9dd3c0af6ad06ce4ed5d3d8504db6f5e5eaaf6c4177889cddd1005da

Tx prefix hash: 6f4427c309c47f4fac87661b6687c688df3161ce219262b794029bb93148fc1a
Tx public key: 07d090274baa63eaa3f42bd544df9e97a6dacf3ac2d283345859085d532d81cc
Timestamp: 1743200612 Timestamp [UCT]: 2025-03-28 22:23:32 Age [y:d:h:m:s]: 00:305:06:31:21
Block: 1249410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215828 RingCT/type: yes/0
Extra: 0107d090274baa63eaa3f42bd544df9e97a6dacf3ac2d283345859085d532d81cc021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 683ba76d01160105003b45d5de7893c0c3b6cdc619fb4f7d0f1d33d8a6324cc0 0.600000000000 1736449 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": 1249420, "vin": [ { "gen": { "height": 1249410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "683ba76d01160105003b45d5de7893c0c3b6cdc619fb4f7d0f1d33d8a6324cc0" } } ], "extra": [ 1, 7, 208, 144, 39, 75, 170, 99, 234, 163, 244, 43, 213, 68, 223, 158, 151, 166, 218, 207, 58, 194, 210, 131, 52, 88, 89, 8, 93, 83, 45, 129, 204, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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