Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b600256a498291b0084616fe0bfedddd54582057bc20753e03e9f8f6b6129fcb

Tx prefix hash: 98c74fae6297f4a89fb88b97fba125028c54ee9565cc522451df78459c1aacb9
Tx public key: 4d8fe180d0eda6ee250bc9d8aec0b1987be35011a40a5487a9e0b0abf4aa72da
Timestamp: 1734537665 Timestamp [UCT]: 2024-12-18 16:01:05 Age [y:d:h:m:s]: 00:112:23:37:38
Block: 1177994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80514 RingCT/type: yes/0
Extra: 014d8fe180d0eda6ee250bc9d8aec0b1987be35011a40a5487a9e0b0abf4aa72da0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09794eaf754082cb598a9fd3099c324df21eb0ef0ba1ffb4b0c0a4df9720b3cc 0.600000000000 1664377 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": 1178004, "vin": [ { "gen": { "height": 1177994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09794eaf754082cb598a9fd3099c324df21eb0ef0ba1ffb4b0c0a4df9720b3cc" } } ], "extra": [ 1, 77, 143, 225, 128, 208, 237, 166, 238, 37, 11, 201, 216, 174, 192, 177, 152, 123, 227, 80, 17, 164, 10, 84, 135, 169, 224, 176, 171, 244, 170, 114, 218, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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