Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a25e48e64e2f0d84a1650ada0a1e6bab1ef0f7f8e12a87554debbe4bce52bcc2

Tx prefix hash: f8915abf85fe9214fe1adb3edc1b9f059ddc2a44c1719e8b9199a88776b10248
Tx public key: 1cb3bbfb59b70530b4c5b5e678fa2c0e9e2580c5c0242aaff86e3b81035be64a
Timestamp: 1729365934 Timestamp [UCT]: 2024-10-19 19:25:34 Age [y:d:h:m:s]: 00:243:23:05:07
Block: 1135202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174025 RingCT/type: yes/0
Extra: 011cb3bbfb59b70530b4c5b5e678fa2c0e9e2580c5c0242aaff86e3b81035be64a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b0c9977f3f1cee186bf5e02700bc21cdf9a66f0d351bfa14a76f9869421225 0.600000000000 1618533 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": 1135212, "vin": [ { "gen": { "height": 1135202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b0c9977f3f1cee186bf5e02700bc21cdf9a66f0d351bfa14a76f9869421225" } } ], "extra": [ 1, 28, 179, 187, 251, 89, 183, 5, 48, 180, 197, 181, 230, 120, 250, 44, 14, 158, 37, 128, 197, 192, 36, 42, 175, 248, 110, 59, 129, 3, 91, 230, 74, 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