Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4395881d28faa1619df77b364e6978bb2926afcf4bc63451f5e41c95289ab5d5

Tx prefix hash: 84f59e4bc3dbd5a12b425924fb09d6410128d3ffa14e3f872611bbaf97d4b2a8
Tx public key: 299e6279e730d22f4f0555a91ffcbc33a97eb3c4373cd287dda6a0b2e4dbdedb
Timestamp: 1702528035 Timestamp [UCT]: 2023-12-14 04:27:15 Age [y:d:h:m:s]: 01:038:04:30:16
Block: 912706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288602 RingCT/type: yes/0
Extra: 01299e6279e730d22f4f0555a91ffcbc33a97eb3c4373cd287dda6a0b2e4dbdedb02110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26c3a1d720c8cd8a12e4e2af0274f22cd356ad417bb18189032a57d580afbb7a 0.600000000000 1369940 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": 912716, "vin": [ { "gen": { "height": 912706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26c3a1d720c8cd8a12e4e2af0274f22cd356ad417bb18189032a57d580afbb7a" } } ], "extra": [ 1, 41, 158, 98, 121, 231, 48, 210, 47, 79, 5, 85, 169, 31, 252, 188, 51, 169, 126, 179, 196, 55, 60, 210, 135, 221, 166, 160, 178, 228, 219, 222, 219, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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