Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8040c97a1e273b31322d1ea0d9b281858520eb5346fb8bc26b81be644da89f76

Tx prefix hash: 413c059e1ee09c064e8ce2040a5b7e7494cdc920bf4c684b9ce9d4356235dd47
Tx public key: 43a934f8b70e1f860f97e42b077f834e6dd9b505c9694ca23031b5752e36025a
Timestamp: 1723744130 Timestamp [UCT]: 2024-08-15 17:48:50 Age [y:d:h:m:s]: 00:308:11:01:03
Block: 1088593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220245 RingCT/type: yes/0
Extra: 0143a934f8b70e1f860f97e42b077f834e6dd9b505c9694ca23031b5752e36025a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fb982b131f22e62da0dc82446b1d869bba1975ca82eb8be7896422512ad731d 0.600000000000 1563210 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": 1088603, "vin": [ { "gen": { "height": 1088593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fb982b131f22e62da0dc82446b1d869bba1975ca82eb8be7896422512ad731d" } } ], "extra": [ 1, 67, 169, 52, 248, 183, 14, 31, 134, 15, 151, 228, 43, 7, 127, 131, 78, 109, 217, 181, 5, 201, 105, 76, 162, 48, 49, 181, 117, 46, 54, 2, 90, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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