Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07e39eac88bdceba84a9c0ec1a6258be2c5e0544a6281db30454c302d427406a

Tx prefix hash: b8483f13aafb50f18b4f3f17208a125afa55c1a60996ec38f3189a7a634b6960
Tx public key: 02336ec61e85fc9c1b43c33de29c0a73e9303c883a7f86cbe7e9fefadd1c7dd1
Timestamp: 1727806531 Timestamp [UCT]: 2024-10-01 18:15:31 Age [y:d:h:m:s]: 00:054:07:49:37
Block: 1122281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38803 RingCT/type: yes/0
Extra: 0102336ec61e85fc9c1b43c33de29c0a73e9303c883a7f86cbe7e9fefadd1c7dd102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4575ac4a236a7cd5cf66473255a2dbbc57fc5d0b35ac75cece00521b97bd221f 0.600000000000 1604692 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": 1122291, "vin": [ { "gen": { "height": 1122281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4575ac4a236a7cd5cf66473255a2dbbc57fc5d0b35ac75cece00521b97bd221f" } } ], "extra": [ 1, 2, 51, 110, 198, 30, 133, 252, 156, 27, 67, 195, 61, 226, 156, 10, 115, 233, 48, 60, 136, 58, 127, 134, 203, 231, 233, 254, 250, 221, 28, 125, 209, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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