Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32fbed7a2a8821d1d5d11f5dc55bdcd2f8aa12a9c91e4bc5799145ba14b5dbf1

Tx prefix hash: 608bb60a0d54050f7e7083b3a60bfdcb0018f3f636bb829996513fd7dda73ce7
Tx public key: b92077afb2c4f39151e099f5d0baa007f971fbd8f86a0a9de5d18a78d291a077
Timestamp: 1737249375 Timestamp [UCT]: 2025-01-19 01:16:15 Age [y:d:h:m:s]: 00:056:22:20:44
Block: 1200377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40507 RingCT/type: yes/0
Extra: 01b92077afb2c4f39151e099f5d0baa007f971fbd8f86a0a9de5d18a78d291a077021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0b25234ab19af5b4c016f93f3cf304dc461b786795fb5dc8e34368c3b17d0fa 0.600000000000 1687020 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": 1200387, "vin": [ { "gen": { "height": 1200377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0b25234ab19af5b4c016f93f3cf304dc461b786795fb5dc8e34368c3b17d0fa" } } ], "extra": [ 1, 185, 32, 119, 175, 178, 196, 243, 145, 81, 224, 153, 245, 208, 186, 160, 7, 249, 113, 251, 216, 248, 106, 10, 157, 229, 209, 138, 120, 210, 145, 160, 119, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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